Start transitioning to Git for Windows' new Pacman repository #113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To disentangle Git for Windows' Pacman repository from my personal Azure account a bit, I started transitioning it to https://github.com/git-for-windows/pacman-repo.
In git-for-windows/build-extra#595, I prepare
pacman-helper.sh
(which is Git for Windows' work horse for Pacman package deployments) to dual-deploy both to the old and to the new Pacman repository. Naturally, this needs the appropriate GitHub token to work. So here is the PR to adjust the two remaining call sites in Git for Windows' automation to provide said token.